Every assessment, read properly.
Every judgement, still yours.

Apollo reads each learner’s work against your marking guide and drafts the marks.

Most of a marking hour is spent looking things up.

Re-reading the guide, finding the right paragraph. Apollo does that part, then stops.

Student evidence. Your requirements. Your marking guide.

Load your marking guide and sample answers, and check each task’s setup. Apollo works out what kind of task it is.

A drafted tick or cross for each requirement.

A real draft judgement · demo data · the assessor decides

Your assessor confirms, changes or overrules. Then signs.

Apollo can’t finalise a result on its own. The returned document shows the assessor’s name and when they signed.

One learner, or the whole cohort at once.

Word, Excel, PDF or scans, just as learners handed them in. No retyping.

One guide for the whole batch.

Large batches are normal, and that’s where most of the time is saved. Once each task’s guide is checked, every assessor marks against it.

Every submission, compared with every other.

Every answer is compared with every other, and with the sample answer, on your own computer. Most comparisons find nothing.

A comparison no one could do by hand across a whole cohort.

Apollo shows where answers look unusually alike. It doesn’t search the internet or past classes. An AI second look is optional, with names removed first.

Individual results become unit-level insight.

Apollo keeps the patterns, not the learners’ work.

Apollo shows where to look. People work out why.

Hard tasks, common mistakes and possible problems with the assessment, shown by task and question.

A unit is a set of documents that have to agree with each other.

Apollo reads your unit’s documents side by side, like an auditor would, before validation.

Performance criterion 2.2: no clear assessment evidence.

If a task asks for something the guide never checks, Apollo shows you where.

The real Cross-Check report · demo data, fictional RTO · an assessor decides what to act on

Apollo gives your validators a clear list to review. It doesn’t do the validation.

Marking feeds insight. Insight points to the unit. The unit gets better.

Marking shows a pattern. The Cross-Check finds the cause. You fix the task. The next class shows if it worked.

Keep the systems that run your RTO.
Improve what happens around assessment.

Your SMS, LMS and templates stay as they are. Apollo takes your files and gives back marked work.

Exported as usual.

Read, drafted and checked by a person.

Returned marked and signed. Your records never moved.

24 assessments. One trainer. Same unit, same guide.

Six and a half hours, by her estimate.

Two hours, timed by her. Every judgement still hers.

After sign-off, the batch is gone. Learner submissions are never stored: they’re held in your browser and cleared when you reload or sign out.

Better marking.
Better assessment.
Better decisions.

Run one unit through Apollo and measure your own turnaround and hours against last term.